Hi Bill,

Rapid moves use the Velocity, Acceleration, and Jerk settings in KFLOP (ie Step Response Screen).  If you make such a big move from the KMotion Step Response Screen do you experience the same problem?

A common problem is to configure a velocity way too high for your system but never test it on long enough move to accelerate up to a too high of a speed.   If you then command a longer move the trajectory will exceed the velocity capability of the axis.  The axis will then fall way behind.  If you have small following error limits this will immediately fault and stop the axis.  But if you don't, then the axis will simply fall far behind the trajectory.  Eventually after the trajectory stops the axis will catch up and come to an abrupt uncontrolled stop.

Could this be what is occurring?

Regards

TK

Group: DynoMotion	Message: 9942	From: Tom Kerekes	Date: 8/10/2014
Subject: Re: Y axis

Hi Bill, It wouldn't actually be an issue of still accelerating.  It is like trying to track someone in a car that can go 100MPH in a car that can only go 95MPH.  In town there is no problem.  But on a long stretch of road he would pull far away from you.  Eventually some time after he stops you will catch up to him and slam into him.  How gradually he comes to a stop will not matter because at that time you would be still racing full speed trying to catch up. The first thing to check is your Max Following error.  You didn't post what it is.  If set to a small value then this is not the issue or there would simply be a following error fault when the axis begins to fall behind the trajectory. G0 Rapids always come to a full stop after each segment so I don't see how the Trajectory Planner setting could cause an unusual stop. The best diagnostic approach for something like this is to capture motion data to a file and then plot it out to see exactly what happened. HTH Regards TK   Group: DynoMotion Message: 9943 From: Wcarrothers Yahoo Date: 8/10/2014 Subject: Re: Y axis I will start into looking at it next week.  I will post my follow error Not sure i can produce the symptom in a plot seeing it has to move a long way before this will do it.   The setup does have a very high jerk number.  I have it that way seeing that is how it is set when tuning.  If it should be dialed back for normal operation I can do that just never did it for either machines.  The other machine is an analog one so probably don't see it there seeing the secondary control involved.  Other wise it is working really wellb On Aug 10, 2014, at 11:48 AM, "Tom Kerekes tk@... [DynoMotion]" <DynoMotion@yahoogroups.com> wrote:   Hi Bill, It wouldn't actually be an issue of still accelerating.  It is like trying to track someone in a car that can go 100MPH in a car that can only go 95MPH.  In town there is no problem.  But on a long stretch of road he would pull far away from you.  Eventually some time after he stops you will catch up to him and slam into him.  How gradually he comes to a stop will not matter because at that time you would be still racing full speed trying to catch up. The first thing to check is your Max Following error.  You didn't post what it is.  If set to a small value then this is not the issue or there would simply be a following error fault when the axis begins to fall behind the trajectory. G0 Rapids always come to a full stop after each segment so I don't see how the Trajectory Planner setting could cause an unusual stop. The best diagnostic approach for something like this is to capture motion data to a file and then plot it out to see exactly what happened. HTH Regards TK